Prevent conflicts between pattern pull requests - #222
Merged
Conversation
Derive navigation from per-pattern ordering, shard social drafts, and make the social queue automation-owned so pattern additions no longer edit shared files. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a96222e0-ecf3-48eb-9141-4e52f0c61308
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concurrent pattern pull requests currently edit reciprocal navigation links and aggregate social files, so merging one PR frequently makes the others conflict. This change moves those responsibilities out of shared contributor-owned files.
Approach
prev/nextlinks with per-patternnavigationOrder; the generator derives a deterministic global chain using the pattern key as a tie-breaker.social/tweets.yamlinto one reviewable draft per pattern undersocial/tweets/{category}/{slug}.yaml.social/queue.txtto a pending-only queue managed by serialized automation, withpostedKeystracking the current cycle.Migration notes
The migration preserves all 135 existing tweet drafts verbatim and keeps
collections/map-entry-factoryas the next scheduled post. It also establishes one complete navigation sequence for all 135 patterns, including the six patterns that were disconnected after the recent concurrent merges.